Process Governance Framework

The Process Governance Framework (as it is called in this Help) is a document that allows an organisation to record all the requirements for those who are producing information for their Process Library, i.e. the Process maps, but also, if required, the documentation, e.g. policies, procedures, work instructions and forms. This document should be a policy document and any additional details may be included in a Work Instruction.

An example of the contents could be:

• Naming and Numbering conventions
• Identification - how will you uniquely identify maps and documents
• Issue Numbering - how will you indicate the different version of maps and documents
• Map Naming - how will the maps be named, e.g. as verbs (see Naming the Node)
• Document Naming - any rules on document titles
• Requirements for Process Maps
• Design (Stencil and Template) - this should include a list of all the shapes to be used and any rules on their use
• Properties - this would state the Properties (see Properties File) and what information is required
• Roles - this could list all the roles to be used on the activities and the list of Process Owners for the Maps
• Drawing the maps - any rules for drawing the maps, e.g. not more that four activities across a page unless absolutely necessary
• Linking to other maps, document and locations - defines how to link to other maps, documents or folder locations
• Common and Reusable Processes - some short processes may be linked to more than one activity, so cannot be drilled down in the normal way; what are the rules about these processes and how do you link to them
• Storage and Archiving - the current maps will be stored in the mapstore, but you may have subfolders within it. How will you archive previous versions of the maps?
• Requirements for Documentation
• Look and Feel - this should list any templates to be used for a consistent look and feel of the documents
• Writing Style - is there a specific writing style to be used
• Signatures - if signatures are required for documents, how will this be managed?
• This page intentionally left blank - if there is a requirements for no pages to be left blank, state how you will ensure this
• Storing and Archiving - how will the documents be stored and previous versions archived?
• Linking to Maps and Menus - if there is a need to link to maps, menus and other documents, what are the rules for this?
• Requirements for the Forms
• Look and Feel - what are the rules for forms to ensure consistency?
• Storage and Archiving - how will the empty forms be stored and previous versions archived?
• On the Triaster Server
• Access - who will have access to the Administration and Approval pages?
• Front pages - this describes front pages of the Process Library, i.e. the home page and the pages which will contain the menus. They are usually in Corporate Branding colours and design. This section could include a screenshot of the front pages.
• Menu pages - what are the rule on how the menu pages are constructed
• Reports - what reports will be used. This will include standard reports not required and the use of customised reports.
• Folders - what is the folder structure on the server for the Mapstore, Documents and other areas for the Administrator.
• Approving - how will the maps be approved and by whom?
• Reviewing - how will the maps be reviewed, by whom and how often?